Repository navigation
docs: add Prayu security policy - #2
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
SECURITY.mdtailored to Prayu's local-first Agent security boundariesmain-only remediation targetWhy
The repository previously had no dedicated vulnerability reporting policy. Prayu handles credentials, durable local state, model/Provider traffic, filesystem proposals, and controlled execution surfaces, so reporters need a clear path that does not accidentally expose sensitive material in a public Issue.
GitHub Private Vulnerability Reporting is currently disabled for this repository. The policy therefore links to the repository's real Security page, tells reporters to use the private form if it becomes available, and documents the maintainer's public contact email as the current private-first fallback.
Impact
Documentation only. This PR changes no runtime code, policy decision, capability, execution gate, or security boundary.
Validation
git diff --checkenabled=false